Moderate: Red Hat Enterprise MRG Messaging 2.1 security and enhancement update

Related Vulnerabilities: CVE-2011-3620   CVE-2011-3620  

Synopsis

Moderate: Red Hat Enterprise MRG Messaging 2.1 security and enhancement update

Type/Severity

Security Advisory: Moderate

Topic

Updated Messaging packages that resolve one security issue, fix multiple
bugs, and add various enhancements are now available for Red Hat Enterprise
MRG 2.1 for Red Hat Enterprise Linux 5.

The Red Hat Security Response Team has rated this update as having moderate
security impact. A Common Vulnerability Scoring System (CVSS) base score,
which gives a detailed severity rating, is available from the CVE link in
the References section.

Description

Red Hat Enterprise MRG (Messaging, Realtime, and Grid) is a next-generation
IT infrastructure for enterprise computing. MRG offers increased
performance, reliability, interoperability, and faster computing for
enterprise customers.

MRG Messaging is a high-speed reliable messaging distribution for Linux
based on AMQP (Advanced Message Queuing Protocol), an open protocol
standard for enterprise messaging that is designed to make mission critical
messaging widely available as a standard service, and to make enterprise
messaging interoperable across platforms, programming languages, and
vendors. MRG Messaging includes an AMQP 0-10 messaging broker; AMQP 0-10
client libraries for C++, Java JMS, and Python; as well as persistence
libraries and management tools.

It was found that Qpid accepted any password or SASL mechanism, provided
the remote user knew a valid cluster username. This could give a remote
attacker unauthorized access to the cluster, exposing cluster messages and
internal Qpid/MRG configurations. (CVE-2011-3620)

Note: If you are using an ACL, the cluster-username must be allowed to
publish to the qpid.cluster-credentials exchange. For example, if your
cluster-username is "foo", in your ACL file:

acl allow foo@QPID publish exchange name=qpid.cluster-credentials

The CVE-2011-3620 fix changes the cluster initialization protocol. As such,
the cluster with all new version brokers must be restarted for the changes
to take effect. Refer below for details.

These updated packages provide numerous enhancements and bug fixes for the
Messaging component of MRG. Space precludes documenting all of these
changes in this advisory. Documentation for these changes will be available
shortly in the Technical Notes document linked to in the References
section.

All users of the Messaging capabilities of Red Hat Enterprise MRG 2.1 are
advised to upgrade to these updated packages, which resolve the issues and
add the enhancements noted in the Red Hat Enterprise MRG 2 Technical Notes.
After installing the updated packages, stop the cluster by either running
"service qpidd stop" on all nodes, or "qpid-cluster --all-stop" on any one
of the cluster nodes. Once stopped, restart the cluster with
"service qpidd start" on all nodes for the update to take effect.

Solution

Before applying this update, make sure all previously-released errata
relevant to your system have been applied.

This update is available via the Red Hat Network. Details on how to
use the Red Hat Network to apply this update are available at
https://access.redhat.com/knowledge/articles/11258

Affected Products

  • MRG Grid from RHUI 2 for RHEL 5 x86_64
  • Red Hat Enterprise MRG Messaging 2 for RHEL 5 x86_64
  • Red Hat Enterprise MRG Messaging 2 for RHEL 5 i386
  • MRG Grid 2 for RHEL 5 x86_64
  • MRG Grid 2 for RHEL 5 i386

Fixes

  • BZ - 650969 - [RFE] qpid-winsdk should support Microsoft Visual Studio 2010
  • BZ - 674379 - [RFE] IPv6 support for qpid C++ messaging
  • BZ - 691654 - qpidd broker triggers SELinux AVCs avc: denied { search } for pid=27642 comm="qpidd" name="/" dev=sysfs ino=1 scontext=unconfined_u:system_r:qpidd_t:s0 tcontext=system_u:object_r:sysfs_t:s0 tclass=dir
  • BZ - 700632 - qpid-java-common rpm erroneously includes qpid-ra-0.10.jar
  • BZ - 704596 - The toString() representation of the JMSDestination of a received message is different from the toString() representation on the sender side.
  • BZ - 705418 - Ability to acknowledge all messages up to and including a given message for a Session
  • BZ - 726102 - cpp client parsing error when dealing with empty strings
  • BZ - 727182 - Support DTX transactions in a cluster.
  • BZ - 730981 - Unable to create binding while sending messages on default exchange using addressing
  • BZ - 731368 - Only one message is consumed using c++ drain by default
  • BZ - 733241 - 'qpid-config queues <queue_name>' should return proper error code
  • BZ - 733383 - Single message can be delivered to multiple client
  • BZ - 734729 - qpidd broker crash during shutdown
  • BZ - 735208 - management of store/journal no longer available
  • BZ - 747078 - CVE-2011-3620 qpid-cpp: cluster authentication ignores cluster-* settings
  • BZ - 751845 - Allow SSL and non-SSL connections on the same port
  • BZ - 760112 - Journal management stats not available for recovered queues
  • BZ - 760636 - Message Group query method should include message timestamp if present.
  • BZ - 761186 - Java client mishandles tcp_nodelay when specified as part of the broker URL

CVEs

References